home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950528-19950726
/
000033_news@columbia.edu_Tue May 30 11:16:28 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA19599
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Fri, 2 Jun 1995 04:49:43 -0400
Received: by apakabar.cc.columbia.edu id AA17303
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 2 Jun 1995 04:49:42 -0400
Path: news.columbia.edu!panix!news.mathworks.com!news.kei.com!nntp.et.byu.edu!news.provo.novell.com!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Automating kermit session in a shell script
Message-Id: <1995May30.171628.52777@cc.usu.edu>
Date: 30 May 95 17:16:28 MDT
References: <3qfuqp$l9f@CUBoulder.Colorado.EDU>
Distribution: na
Organization: Utah State University
Lines: 24
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3qfuqp$l9f@CUBoulder.Colorado.EDU>, grubin@spot.Colorado.EDU (Rick Grubin) writes:
>
> I would like to automate a kermit session between two hosts
> in a shell script (or DOS batch file, either way is acceptable).
> The two computers in question are connected directly via a serial
> connection (null modem cable) or via a local network. The goal
> is to have one computer (either a DOS or Unix host) connect to
> a Unix computer, establish a remote kermit server, jump back to
> the connect-initiating computer, send files, and then finish the
> remote server on the Unix computer.
>
> I can do this manually, with no difficulty. I am struggling
> with getting past the "login/password" sequence on the remote
> Unix computer, as well as the "escape back to initiating computer"
> character sequence, in both Unix shell script and DOS batch files.
> Any help with automating this procedure from DOS batch files or
> Unix shell scripts would be most appreciated. Thank you in advance.
--------
Have you considered the best way might be to use the scripting
language (sic) provided by Kermits? One end starts and does the login
chatter, invokes the other Kermit, then swap files and other tall stories,
then the script does the goodbyes. Have a look at the full documentation
and explanation in the user's manuals, the "Using MS-DOS / C Kermit" books.
Joe D.